home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX Base Documentation 1998 November
/
IRIX 6.5.2 Base Documentation November 1998.img
/
usr
/
share
/
catman
/
u_man
/
cat1
/
egrep.z
/
egrep
Wrap
Text File
|
1998-10-20
|
5KB
|
133 lines
EEEEGGGGRRRREEEEPPPP((((1111)))) EEEEGGGGRRRREEEEPPPP((((1111))))
NNNNAAAAMMMMEEEE
egrep - search a file for a pattern using full regular expressions
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
eeeeggggrrrreeeepppp [options] full regular expression [file ...]
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
_e_g_r_e_p (_e_x_p_r_e_s_s_i_o_n _g_r_e_p) searches files for a pattern of characters and
prints all lines that contain that pattern. _e_g_r_e_p uses full regular
expressions (expressions that have string values that use the full set of
alphanumeric and special characters) to match the patterns. It uses a
fast deterministic algorithm that sometimes needs exponential space.
_e_g_r_e_p accepts full regular expressions as in _e_d(1), except for \\\\(((( and \\\\)))),
and except for \\\\<<<< and \\\\>>>>, with the addition of:
1. A full regular expression followed by ++++ that matches one or more
occurrences of the full regular expression.
2. A full regular expression followed by ???? that matches 0 or 1
occurrences of the full regular expression.
3. Full regular expressions separated by |||| or by a new-line that match
strings that are matched by any of the expressions.
4. A full regular expression that may be enclosed in parentheses (((())))
for grouping.
Be careful using the characters $$$$, ****, [[[[, ^^^^, |, ((((, )))), and \\\\ in _f_u_l_l
_r_e_g_u_l_a_r _e_x_p_r_e_s_s_i_o_n, because they are also meaningful to the shell. It is
safest to enclose the entire _f_u_l_l _r_e_g_u_l_a_r _e_x_p_r_e_s_s_i_o_n in single quotes
''''...''''.
The order of precedence of operators is [[[[]]]], then ****????++++, then concatenation,
then |||| and new-line.
If no files are specified, _e_g_r_e_p assumes standard input. Normally, each
line found is copied to the standard output. The file name is printed
before each line found if there is more than one input file.
Command line options are:
----bbbb Precede each line by the block number on which it was found. This
can be useful in locating block numbers by context (blocks are 512
bytes long and number from 0).
----cccc Print only a count of the lines that contain the pattern.
----hhhh Suppresses printing of filenames when searching multiple files.
----iiii Ignore upper/lower case distinction during comparisons.
----llll Print the names of files with matching lines once, separated by
new-lines. Does not repeat the names of files when the pattern is
found more than once.
----nnnn Precede each line by its line number in the file (first line is 1).
----ssss Silent mode. No pattern matches or error messages are printed.
This option allows command expressions to check _e_g_r_e_p's exit status
without having to deal with output.
PPPPaaaaggggeeee 1111
EEEEGGGGRRRREEEEPPPP((((1111)))) EEEEGGGGRRRREEEEPPPP((((1111))))
----vvvv Print all lines except those that contain the pattern.
----eeee _s_p_e_c_i_a_l__e_x_p_r_e_s_s_i_o_n
Search for a _s_p_e_c_i_a_l _e_x_p_r_e_s_s_i_o_n (_f_u_l_l _r_e_g_u_l_a_r _e_x_p_r_e_s_s_i_o_n that
begins with a ----).
----ffff _f_i_l_e
Take the list of _f_u_l_l _r_e_g_u_l_a_r _e_x_p_r_e_s_s_i_o_n_s from _f_i_l_e.
SSSSEEEEEEEE AAAALLLLSSSSOOOO
ed(1), fgrep(1), grep(1), sed(1), sh(1).
DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
Exit status is 0 if any matches are found, 1 if none, 2 for syntax errors
or inaccessible files (even if matches were found).
BBBBUUUUGGGGSSSS
Ideally there should be only one _g_r_e_p command, but there is not a single
algorithm that spans a wide enough range of space-time tradeoffs. Lines
are limited to BUFSIZ characters; longer lines are truncated. BUFSIZ is
defined in ////uuuussssrrrr////iiiinnnncccclllluuuuddddeeee////ssssttttddddiiiioooo....hhhh....
PPPPaaaaggggeeee 2222